Algorithm for managing data loss in software demodulators

ABSTRACT

Embodiments of methods for receiving and processing multi-band signals in wideband and narrowband environments are described herein. Other embodiments may be described and claimed.

FIELD OF THE INVENTION

The field of invention relates generally to a multi-band wireless systemand more specifically but not exclusively relates to methods forreceiving and processing multi-band signals in wideband and/ornarrowband environments.

BACKGROUND INFORMATION

Technological developments permit digitization of large amounts ofvoice, video, imaging, and data information from a transmitting stationto a receiving station. One emerging application is the deployment ofdigital television, including handheld-oriented broadcast services thatcan withstand mobility of the receiving stations. For example, digitalvideo broadcasting-handheld (DVB-H) and terrestrial-digital multimediabroadcasting (T-DMB) are deployed in mobile TV applications whiledigital video broadcasting-terrestrial (DVB-T) is already widelydeployed for nomadic to portable reception conditions.

The need to transfer data between stations in wireless radiocommunication requires transfer of a reliable data stream betweenstations and internally within each station. Depending upon underlyingtransfer mechanisms, certain data transfers may require the bufferingand storage of data blocks. For example, in a universal serial bus (USB)implementation, isochronous data transfers may be utilized to transmitdigital television data to a storage location before demodulation by asoftware demodulator. Incoming isochronous data flows when stored in afixed buffer location can lead to buffer overruns and data loss if thedata is not regularly transferred from the buffer to a processor,leading to data synchronization issues.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and not as alimitation in the figures of the accompanying drawings, in which:

FIG. 1 is a block diagram of one embodiment of a networking environment.

FIG. 2 is an embodiment of a method for buffering of channel data forsoftware demodulation.

FIG. 3 is an embodiment of a computing system for software demodulationof narrowband channel data.

FIG. 4 is an embodiment of a memory for buffering of narrowband channeldata.

FIG. 5 is a block diagram of an embodiment of a mobile device configuredfor hardware and software demodulation.

FIG. 6 is an alternate embodiment of a method for buffering of channeldata for software demodulation.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of the invention.However, it will be understood by those skilled in the art that thepresent invention may be practiced without these specific details. Inother instances, well-known methods, procedures, components and circuitshave not been described in detail so as not to obscure the presentinvention.

Embodiments of methods and systems for managing data loss in a computingsystem are described herein. In the following description, numerousspecific details are set forth such as a description of a mechanism forreducing or eliminating data transfer synchronization errors inmulti-band wireless systems to provide a thorough understanding ofembodiments of the invention. One skilled in the relevant art willrecognize, however, that the invention can be practiced without one ormore of the specific details, or with other methods, components,materials, etc. In other instances, well-known structures, materials, oroperations are not shown or described in detail to avoid obscuringaspects of the invention.

It would be an advance in the art to provide a data synchronizationmechanism for multi-band wireless systems communicating over a pluralitychannels or spectrum bands to provide a non-interrupted broadcaststream. As an example, wireless stations may comprise a host processor,a flash memory device, a random access memory and a transceiverconfigured to communicate either sequentially or simultaneously overnarrowband and wideband channels.

In one embodiment, a method for maintaining synchronization of datapackets may comprise partitioning the data packets into a plurality ofblocks with headers. A continuity counter is added to the header of eachblock of the plurality of blocks and the plurality of blocks is storedin a buffer memory. An availability of a communication channel ismonitored and one or more of the plurality of blocks is erased when thecommunication channel is not available. The continuity counters aremonitored to determine if one or more blocks have been erased and pseudonoise samples are inserted to replace the one or more erased blocks.

Now turning to the figures, FIG. 1 illustrates various components of anetworking environment 100 which may be utilized to implement variousembodiments discussed herein. The environment 100 may include a network102 to enable communication between various devices such as a server104, a desktop computer 106 such as, for example, a workstation or adesktop computer, a laptop, netbook, or notebook computer 108, areproduction device 110, such as, for example, a network printer,copier, facsimile, scanner, all-in-one device, etc., a wireless accesspoint 112, which may comprise a cellular base station in variousembodiments, and a personal digital assistant, smartphone, or mobiledevice 114. The network 102 may be any type of types of a computernetwork including an intranet, the Internet, and/or combinationsthereof.

The devices 104-114 may communicate with the network 102 through wiredand/or wireless connections. Hence, the network 102 may be a wiredand/or wireless network. For example, as illustrated in FIG. 1, thewireless access point 112 may be coupled to the network 102 to enableother wireless-capable devices, such as the device 114 for example, tocommunicate with the network 102. In various embodiments, the wirelessaccess point 112 may include traffic management capabilities. Also, datacommunicated between the devices 104-114 may be encrypted orcryptographically secured to limit unauthorized access.

The network 102 may utilize any communication protocol such as Ethernet,Fast Ethernet, Gigabit Ethernet, wide-area network (WAN), fiberdistributed data interface (FDDI), Token Ring, leased line, analogmodem, digital subscriber line (DSL) and its varieties such as highbit-rate DSL (HDSL), integrated services digital network DSL (IDSL),etc.), asynchronous transfer mode (ATM), cable modem, and/or FireWire.

Wireless communication through the network 102 may be in accordance withone or more of the following: wireless local area network (WLAN),wireless wide area network (WWAN), code division multiple access (CDMA)cellular radiotelephone communication systems, global system for mobilecommunications (GSM) cellular radiotelephone systems, North AmericanDigital Cellular (NADC) cellular radiotelephone systems, time divisionmultiple access (TDMA) systems, extended TDMA (E-TDMA) cellularradiotelephone systems, third generation partnership project (3G)systems such as wide-band CDMA (WCDMA), etc. Moreover, networkcommunication may be established by internal network interface devices(e.g., present within the same physical enclosure as a computing system)such as a network interface card (NIC) or external network interfacedevices (e.g., having a separate physical enclosure and/or power supplythan the computing system to which it is coupled).

Further, digital television signals may be communicated along widebandand narrowband channels in the networking environment 100. Examples ofwideband channel data in frequencies ranging from 5 to 8 megahertz (MHz)comprise digital video broadcasting terrestrial (DVB-T) and/or digitalvideo broadcasting handheld (DVB-H) applications. Examples of narrowbandchannel data in frequencies substantially at or near 1.5 MHz includeterrestrial digital multimedia broadcasting (T-DMB), digital audiobroadcast (DAB), and single segment integrated services digitalbroadcasting terrestrial (ISDB-T) applications. The narrowband and/orwideband channel data is demodulated using hardware and/or softwaremeans by one or more of the devices 104-114.

FIG. 2 is a flowchart of one embodiment for software demodulation ofchannel data. In this embodiment, the channel data is demodulated by analgorithm using a host processor. In element 200, data packets arereceived by a mobile device 114. The data packets are portioned into aplurality of blocks in element 205 of a selected size, such as a blocksize of 128 samples though the embodiment is not so limited. In otherembodiments, the block size may be 64 samples or 256 samples in size.The plurality of blocks is stored in a buffer and a header is added toeach block in elements 210 and 215. The buffer may be a hardware datacollection module (HDCM) in the form of a volatile memory space such asa form of serial access memory (SAM) or a non-volatile memory space suchas a flash memory.

A continuity counter is provided in each header which, in one example isa byte wide, though the embodiment is not so limited. In anotherembodiment, the header may be several blocks wide depending on theinformation provided in each header. The continuity counter in thisexample is a modulo 256 counter that counts from 1 to 255 before rollingback to a zero (0) value. The continuity counter is incremented by onefor every block that is to be transferred.

An availability of a communications channel, such as a pathway providedby a universal serial bus (USB), is monitored for availability inelement 220. The buffer continues to collect and store incoming datapackets until the buffer space has reached a given capacity, which maybe equal to the total storage capacity of the buffer or some otherportion of the total capacity. If the communications channel is busy atthe time that the buffer has reached capacity according to element 225,then one or more blocks are erased in element 230 until thecommunications channel become available in element 240. If the buffer isat capacity but the communications channel is available, then theplurality of blocks is transferred in element 240. The continuitycounters in headers of the plurality of blocks are monitored, in oneembodiment, by a host processor in element 245 to determine if one ormore blocks have been erased, as indicated in element 250. The hostprocessor determines a number of lost blocks through a relationshipdescribed in the continuity counter equation:Blocks_lost=CC(n)−CC(n−1)−1 mod 256

where:

CC(n)=continuity counter of the nth block of data, &

mod=modulo

As a first example, if CC(n)=1 and CC(n−1)=254, the equation wouldreturn a value of 2 for Blocks_lost.

As a second example, if CC(n)=254 and CC(n−1)=254, then the minimumnumber of Blocks_lost=255.

As another example, if 256 blocks are lost the continuity counterequation would return a value of Blocks_lost=0. At this point,synchronization might be lost. This may be overcome by choosing acontinuity counter that is greater than 1 byte or 8 bits in length. Inanother embodiment, a synchronization byte is added to the header inaddition to the continuity counter, resulting in 130 byte samples. Inthis embodiment, the host processor receives a sequence of bytes andwill have to achieve byte synchronization at the start after lockingonto several successive synch bytes that are 130 samples apart. Theaddition of a synch byte allows the software demodulator executed by thehost processor to operate without loss of synchronization.

If it has been determined that blocks have been erased, thenpseudo-noise samples are inserted to replace the erased blocks inelement 255 to provide a synchronized set of blocks. In one embodiment,the pseudo-noise samples are normally distributed zero-mean pseudo-noisesamples with a same variance as the data blocks. The synchronized set ofdata blocks are processed by the host processor using the softwaredemodulator in element 260 to provide a demodulated transport stream.Examples of the demodulated stream may be one or more of a DAB, T-DMB,or a ISDB-T transport stream.

FIG. 3 illustrates a block diagram of a computing system 300, inaccordance with various embodiments. One or more of the devices 104-114discussed with reference to FIG. 1 may comprise one or more of thecomponents of the computing system 300. The computing system 300 mayinclude one or more host processors or central processing unit(s) (CPUs)302 (which may be collectively referred to herein as “processors 302” ormore generally “processor 302”) coupled to an interconnection network orbus 304. The processors 302 may be any type of processor such as ageneral purpose processor, a network processor (which may process datacommunicated over a computer network (102)), etc. (including a reducedinstruction set computer (RISC) processor or a complex instruction setcomputer (CISC)). Moreover, the processors 302 may have a single ormultiple core design. The processors 302 with a multiple core design mayintegrate different types of processor cores on the same integratedcircuit (IC) die. Also, the processors 302 with a multiple core designmay be implemented as symmetrical or asymmetrical multiprocessors.

The processor 302 may include one or more caches 303, which may beprivate and/or shared in various embodiments. Generally, a cache storesdata corresponding to original data stored elsewhere or computedearlier. To reduce memory access latency, once data is stored in acache, future use may be made by accessing a cached copy rather thanrefetching or recomputing the original data. The cache 303 may be anytype of cache, such a level 1 (L1) cache, a level 2 (L2) cache, a level3 (L-3), a mid-level cache, a last level cache (LLC), etc. to storeelectronic data (e.g., including instructions) that is utilized by oneor more components of the computing system 300.

A chipset 306 may additionally be coupled to the interconnection network304. The chipset 306 may include a memory control hub (MCH) 308. The MCH308 may include a memory controller 310 that is coupled to a memory 312.The memory 312 may store data, e.g., including sequences of instructionsthat are executed by the processor 302, or any other device incommunication with components of the computing system 300. In variousembodiments, the memory 312 may include one or more volatile storage ormemory devices such as random access memory (RAM), dynamic RAM (DRAM),synchronous DRAM (SDRAM), static RAM (SRAM), etc. Nonvolatile memory mayalso be utilized such as a hard disk. Additional devices may be coupledto the interconnection network 304, such as multiple processors and/ormultiple system memories.

The MCH 308 may further include a graphics interface 314 coupled to adisplay 316, e.g., via a graphics accelerator. In various embodiments,the graphics interface 314 may be coupled to the display device 316 viaan accelerated graphics port (AGP). In various embodiments, the displaydevice 316, which, for example may include a flat panel display or acathode ray tube, may be coupled to the graphics interface 314 through,for example, a signal converter that translates a digital representationof an image stored in a storage device such as video memory or systemmemory into display signals that are interpreted and displayed by thedisplay. The display signals produced by the display device 316 may passthrough various control devices before being interpreted by andsubsequently displayed on the display device 316.

As shown in FIG. 3, a hub interface 318 may couple the MCH 308 to aninput/output control hub (ICH) 320. The ICH 320 may provide an interfaceto input/output (I/O) devices coupled to the computing system 300. TheICH 320 may be coupled to a bus 322 through a peripheral bridge or hostcontroller 324, such as a peripheral component interconnect (PCI)bridge, a universal serial bus (USB) controller, etc. The controller 324may provide a data path between the processor 302 and peripheraldevices. Other types of topologies may be utilized. Also, multiple busesmay be coupled to the ICH 320, for example, through multiple bridges orcontrollers. For example, the bus 322 may comply with the UniversalSerial Bus Specification, Revision 1.1, Sep. 23, 1998, and/or UniversalSerial Bus Specification, Revision 2.0, Apr. 27, 2000 (includingsubsequent amendments to either revision). Alternatively, the bus 322may comprise other types and configurations of bus systems. Moreover,other peripherals coupled to the ICH 320 may include, in variousembodiments, integrated drive electronics (IDE) or small computer systeminterface (SCSI) hard drive(s), USB port(s), a keyboard, a mouse,parallel port(s), serial port(s), floppy disk drive(s), digital outputsupport (e.g., digital video interface (DVI)), etc.

The bus 322 may be coupled to an audio device 326, one or more diskdrive(s) 328, and a communication device 330, which in variousembodiments may be a network interface card (NIC) or a tuner card. Otherdevices may be coupled to the bus 322. Also, various components such asthe communication device 330 may be coupled to the MCH 308 in variousembodiments. In addition, the processor 302 and the MCH 308 may becombined to form a single chip.

Additionally, the computing system 300 may include volatile and/ornonvolatile memory or storage. For example, nonvolatile memory mayinclude one or more of the following: read-only memory (ROM),programmable ROM (PROM), erasable PROM (EPROM), electrically EPROM(EEPROM), a disk drive (e.g., 328), a floppy disk, a compact disk ROM(CD-ROM), a digital versatile disk (DVD), flash memory, amagneto-optical disk, or other types of nonvolatile machine-readablemedia capable of storing electronic data including instructions.

The memory 312 may include one or more of the following in variousembodiments: an operating system (O/S) 332, application 334, devicedriver 336, buffers 338, function driver 340, and/or protocol driver342. Programs and/or data stored in the memory 312 may be swapped intothe disk drive 328 as part of memory management operations. Theprocessor(s) 302) executes various commands and processes one or morepackets 346 with one or more computing devices coupled to the network102 (such as the devices 104-114 of FIG. 1). In various embodiments, apacket may be a sequence of one or more symbols and/or values that maybe encoded by one or more electrical signals transmitted from at leastone sender to at least one receiver (e.g., over a network such as thenetwork 102). For example, each packet 346 may have a header 346A thatincludes information that may be utilized in routing and/or processingof the packet 346 may comprise the continuity counter, a sync byte,source address, a destination address, packet type, etc. Each packet mayalso have a payload 346B that includes the raw data or content thepacket is transferring between various computing devices, for example,the devices 104-114 of FIG. 1, over a computer network such as thenetwork 102.

In various embodiments, the application 334 may utilize the O/S 332 tocommunicate with various components of the computing system 300, e.g.,through the device driver 336 and/or function driver 340. For example,the device driver 336 and function driver 340 may be used for differentcategories, e.g., device driver 336 may manage generic device classattributes, whereas the function driver 340 may manage device specificattributes (such as USB specific commands). In various embodiments, thedevice driver 336 may allocate one or more buffers (338A through 338M)to store packet data, such as the packet payload 346B. One or moredescriptors (not shown) may respectively point to the buffers 338. Invarious embodiments, one or more of the buffers 338 may be implementedas circular ring buffers. Also, one or more of the buffers 338 maycorrespond to contiguous memory pages in various embodiments.Furthermore, a protocol driver 342 may implement a protocol driver toprocess packets communicated over the network 102, according to one ormore protocols. In accordance with various embodiments, as discussedherein forth, reference to “function driver 340” may or may not refer toother types of drivers, e.g., including device driver 336, functiondriver 340, and/or protocol driver 342.

As illustrated in FIG. 3, the communication device 330 may include anetwork protocol layer 350 for implementing the physical communicationlayer to send and receive network packets to and from remote devicesover the network 102. The network 102 may include any type of computernetwork such as those discussed with reference to FIG. 1. Thecommunication device 330 may further include a direct memory access(DMA) engine 352, which may write packet data to buffers 338 to transmitand/or receive data over the network 102. Additionally, thecommunication device 330 may include a controller 354, which may includelogic, such as a programmable processor for example, to performcommunication device related operations. In various embodiments, thecontroller 354 may be a MAC (media access control) component. Thecommunication device 330 may further include a memory 356, such as anytype of volatile/nonvolatile memory (e.g., including one or morecache(s) and/or other memory types discussed with reference to memory312).

In various embodiments, the communication device 330 may include afirmware storage device 360 to store firmware (or software) that may beutilized in management of various functions performed by components ofthe communication device 330. The storage device 360 may be any type ofa storage device such as a non-volatile storage device. For example, thestorage device 360 may include one or more of the following: ROM, PROM,EPROM, EEPROM, disk drive, floppy disk, CD-ROM, DVD, flash memory, amagneto-optical disk, or other types of nonvolatile machine-readablemedia capable of storing electronic data, including instructions.

In various embodiments, communication device 330 may include or comprisea USB tuner card configured to receive and process multimediainformation. The tuner card may comprise a component that receivesdigital television signals for any of devices 104-114 described inFIG. 1. In various embodiments, the tuner card may also function asvideo capture card, allowing the card to record multimedia informationonto a hard disk. In various embodiments, the tuner card may comprise aUSB express card, a USB mini-card, a USB half-mini card or any othersuitable USB form factor card. The tuner card may contain a receiver,tuner, hardware demodulator, and an analog-to-digital converter invarious embodiments.

In various embodiments, the multimedia information comprises a digitaltelevision signal sent over network 102 from a media source (not shown)to the communication device 330. The multimedia information may comprisea constant bit rate signal for a given modulation rate, code rate andguard interval. The multimedia information may comprise generic codingof moving pictures and associated audio information. In variousembodiments, the multimedia information comprises a DAB, T-DMB, ISDB-T,DVB-T/H, or MPEG2 transport stream. The multimedia information maycontain multiple digital television channels or logical streams in eachphysical channel received from the media source. For example, themultimedia information may comprise various digital television channels,such as BBC 1, BBC 2, BBC 3 and BBC 4 in a single physical channel.

In various embodiments, the received multimedia information is convertedfrom an analog signal to a digital signal using an analog-to-digitalconverter in the tuner card. In one embodiment, demodulation of widebandsignals may also occur in the tuner card using a hardware demodulator.Demodulation may occur within the tuner card and/or part of thedemodulation may occur outside the tuner card, for example, by the CPU302. In various embodiments, the filtered multimedia information is sentfrom the communication device 330 to the chipset 306 over bus 322. As aresult of the processing performed in the communication device 330, themultimedia information sent over bus 322 to chipset 306 comprisesvariable bit rate data even though the information received from themedia source comprises constant bit rate data.

In various embodiments, bus 322 may comprise a USB bus. Isochronous modeis one of the four data flow types for USB devices (the others beingControl, Interrupt and Bulk). Isochronous mode is commonly used forstreaming multimedia data types such as video or audio sources. Inisochronous mode, a device can reserve bandwidth on the bus makingisochronous mode desirable for multimedia applications. In variousembodiments, the data transfer described herein utilizes isochronousmode.

FIG. 4 illustrates one embodiment of a memory 400. Memory 400 may berepresentative of, for example, memory 312 or memory 356 shown in FIG.3. As shown in FIG. 4, memory 400 comprises multiple elements, such as adevice driver 436, USB buffers 438A, media buffers 438B and mediacontrol engine 440. The embodiments, however, are not limited to theelements shown in FIG. 4.

Device driver 436 may comprise a component that handles interactionsbetween memory 400 and any of the elements of computing system 300, forexample. Device driver 436 may be responsible for allocating andmanaging buffers 438A and 438B. In various embodiments, device driver436 allocates USB buffers 438A to be as large as the USB processingstack will allow. Device driver 436 may also allocate media buffers438B, the size of media buffers 438B selected to reduce or eliminatelatency when the multimedia information is retrieved.

USB buffers 438A may comprise a permanent or temporary allocation ofmemory to store multimedia information. As shown in FIG. 4, themultimedia information stored in USB buffers 438A may comprisecontiguous or non-contiguous data. If a system operating in isochronousmode attempts to retrieve the multimedia information stored in USBbuffers 438A, contiguous data is transferred in an orderly mannerwithout loss of synchronization and non-contiguous data may betransformed into contiguous data as provided by embodiments of theinvention.

In various embodiments, device driver 436 controls the making of a copyof the multimedia information from USB buffers 438A to media buffers438B. In a case of non-contiguous data, missing blocks of multimediainformation may be replaced with pseudo-noise samples as provided inelement 255 of FIG. 2 to resolve potential synchronization errors whenprocessed by the software demodulator at the processor 302. Thepseudo-noise samples may be noise samples saved in a memory and/or thepseudo-noise samples may be generated using an optional pseudo-numbergenerator (not shown).

Media control engine 440 may comprise a component that controls requestsfor multimedia information. An example of a media control engine 440 isthe Microsoft® DirectShow® application programming interface (API) byMicrosoft® Corporation of Redmond, Wash. DirectShow is a media-streamingarchitecture for the Microsoft Windows® platform that allowsapplications to perform high-quality video and audio playback orcapture. In various embodiments, media control engine 440 may retrieverequested multimedia data from media buffers 438B to fulfill requestsfor specific multimedia information, for example, a specific televisionchannel or program and provide the requested information to processor302 for further processing and playback.

FIG. 5 is a block diagram of an embodiment of a mobile device configuredfor hardware and software demodulation. A tuner 502 is provided toprocess one or more digital television signals, such as wideband andnarrowband signals. The digital television signals may be transferred tothe tuner 502 using a wired or wirelessly over-the-air. Output from thetuner 502 is directed to an analog to digital converter 504 to convertan input analog voltage to a digital output which may be sent to anautomatic gain control module 506 and/or to a channel filter/automaticgain control module 508. The channel filter 508 is selectively designedto parse an incoming data stream among wideband channel data andnarrowband channel data. In this embodiment, the wideband channel data,such as DVB-T and/or DVB-H channel data is directed to a hardwaredemodulator 510. In another embodiment (not shown), widebanddemodulation occurs through software demodulation as replacement for orin conjunction with hardware demodulation provided by the hardwaredemodulator 510. Demodulated wideband data is then directed to a USBinterface 516.

The narrowband channel data is directed to decimation 512 to reduce anumber of samples to be provided for software demodulation. Decimationremoves in a predictable and orderly manner the number of samplestransferred to a hardware data collection module 514. In anotherembodiment (not shown), demodulation 512 is eliminated or reduced assoftware and processor capabilities allow higher throughput of sampleddata. The hardware data collection module (HDCM) 514 is a memory moduleor buffer and operates as previously described in FIG. 2. The buffereddata from the HDCM 514 is transferred to the USB interface 516 when acommunications channel is available to the host processor 518 todemodulate the narrowband data using a software demodulator.

FIG. 6 is an alternate embodiment of a method for buffering of channeldata for software demodulation. In element 600, a unique header patternis established with a processor to indicate a stream of discontinuoussamples. The unique header pattern, for example is a predefined 6-byteword in a header that may be used to flag or alert a processor of acondition. By flagging the processor, such as the processor 302 of FIG.3, the processor is notified of a discontiguous data stream, or a breakin the data. The unique header pattern may be less than 6 bytes, or morethan 6 bytes in other embodiments. Optionally, a shift register may beapplied to prevent headers from matching the unique header pattern. If ashift register is applied, the normal header data is passed through ashift register. If the normal header data processed by the shiftregister should ever become equal to the unique header pattern, then theshift register toggles a bit to stop it from becoming equal to thepre-defined unique header pattern.

A plurality of samples is received in a buffer in element 605 such asthe HDCM 514 of FIG. 5. The plurality of samples collect in the bufferuntil the buffer reaches a capacity in element 610. If a communicationschannel, such as the USB interface 516 of FIG. 5, is busy when thebuffer reaches capacity, then one or more samples are erased in element615. Otherwise, the samples are directed to a software demodulator toprocess a contiguous sample stream in element 640. The number of sampleserased is determined in element 620 and the unique header pattern istransferred to the processor 302 in element 625 to indicate adiscontiguous data stream. A fixed length word is transmitted to theprocessor 302 in element 630 to indicate the number of samples erased.In one embodiment, the fixed length word is two bytes in length. Inother embodiments, the fixed length word is one byte in length orgreater than two bytes in length. Pseudo-noise samples are inserted toreplace the erased samples in element 635 either through generation ofpseudo-noise samples by the processor or by replacing the erased sampleswith pseudo-noise samples from a memory location to provide a contiguoussample stream. The contiguous sample stream is processed in element 640by the processor 302.

Embodiments of this invention may be used as or to support a softwareprogram executed upon some form of processing core (such as a processorof a computer) or otherwise implemented or realized upon or within amachine-readable medium. A machine-readable medium includes anymechanism for storing information in a form readable by a machine (e.g.,a computer). For example, a machine-readable medium can include such asa read only memory (ROM); a random access memory (RAM); a magnetic diskstorage media; an optical storage media; and a flash memory device, etc.

Reference throughout this specification to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment of the present invention. Thus, theappearances of the phrases “in one embodiment” or “in an embodiment” invarious places throughout this specification are not necessarily allreferring to the same embodiment. Furthermore, the particular features,structures, or characteristics may be combined in any suitable manner inone or more embodiments.

Modifications may be made to the invention in light of the abovedetailed description. The terms used in the following claims should notbe construed to limit the invention to the specific embodimentsdisclosed in the specification and the drawings. Rather, the scope ofthe invention is to be determined entirely by the following claims,which are to be construed in accordance with established doctrines ofclaim interpretation.

1. A method for maintaining synchronization of data packets in acomputing system, comprising: receiving data packets by the computingsystem; establishing a unique header pattern with a processor toindicate a discontiguous stream of data packets; partitioning the datapackets into a plurality of blocks; storing the plurality of blocks in abuffer in the computing system; adding a header with a continuitycounter to each block of the plurality of blocks; erasing one or moreblocks of the plurality of blocks to form remaining blocks; transferringthe remaining blocks over a communication channel in the computingsystem; processing the remaining blocks through a shift register;receiving the unique header pattern; determining that the remainingblocks represent a discontiguous data stream, based on the unique headerpattern; and inserting pseudo noise blocks to replace the one or moreerased blocks in the plurality of blocks to provide a stream ofcontiguous data for demodulation.
 2. The method of claim 1, wherein thedata is multimedia data received by the computing system as a stream ofdata packets.
 3. The method of claim 2, further including decimating thedata packets.
 4. The method of claim 1, wherein the pseudo noise blocksare generated by the processor.
 5. The method of claim 1, furtherincluding adding a synchronization byte to the header.
 6. The method ofclaim 1, wherein the data packets comprise wideband data and narrowbanddata.
 7. The method of claim 1, wherein a block size of each block ofthe plurality of blocks is equal to 128 samples.
 8. A method forprocessing multimedia samples in a computing system, comprising:establishing a unique header pattern with a processor in the computingsystem to indicate a discontiguous sample stream; receiving a pluralityof samples in a memory buffer of the computing system; erasing one ormore samples from the plurality of samples when the memory buffer hasreached a capacity to form a number of discontiguous samples;determining a number of erased samples; transferring the unique headerpattern to the processor; transmitting a fixed length word to theprocessor in the computing system to provide the number of erasedsamples; transferring the number of discontiguous samples to theprocessor; processing a header pattern for each sample of the number ofdiscontiguous samples through a shift register; and insertingpseudo-noise samples to replace the erased samples to form a contiguoussample stream.
 9. The method of claim 8, further including using theshift register to prevent the header pattern from matching the uniqueheader pattern.
 10. The method of claim 9, wherein the unique headerpattern is 6 bytes in length.
 11. The method of claim 8, wherein thebuffer is a flash memory.
 12. The method of claim 8, wherein the fixedlength word is two bytes in length.
 13. A system for multi-band wirelesscommunications, comprising: a communication device configured to receivedata packets, wherein the communication device is configured to:partition the data packets into a plurality of blocks; store theplurality of blocks in a buffer; add a header with a continuity counterto each block of the plurality of blocks; erase one or more blocks ofthe plurality of blocks when the buffer is at capacity to form remainingblocks; and establish a unique header pattern with a processor toindicate a discontiguous stream of data packets; the processor to:process the remaining blocks through a shift register; receive theunique header pattern; determine that the remaining blocks represent adiscontiguous data stream based on the unique header pattern; and insertpseudo noise blocks to replace the one or more erased blocks to providea synchronized set of blocks; and a bus to transfer the plurality ofblocks from the communication device to the processor.
 14. The system ofclaim 13, wherein the data packets comprise narrowband data.
 15. Thesystem of claim 13, further including decimating the data packets. 16.The system of claim 13, wherein the pseudo noise blocks are generated bythe processor.
 17. The system of claim 13, further including adding asynchronization byte to the header.
 18. The system of claim 13, whereinthe data packets comprise wideband data and narrowband data.
 19. Thesystem of claim 13, wherein a block size of each block of the pluralityof blocks is equal to 128 samples.